Skip to content

Bug 2034484: feat: bumped library-go#304

Merged
openshift-merge-robot merged 4 commits intoopenshift:masterfrom
eggfoobar:library_go_bump
Dec 21, 2021
Merged

Bug 2034484: feat: bumped library-go#304
openshift-merge-robot merged 4 commits intoopenshift:masterfrom
eggfoobar:library_go_bump

Conversation

@eggfoobar
Copy link
Copy Markdown
Contributor

Bumping the library-go dependency to latest, this should take advantage of leader election changes for SNO clusters proposed in this library-go PR and performance improvements in this PR.

Changes:

  • updated library-go
  • update to use default leader election configs based off of cluster topology
  • updated to k8s v0.23.0
  • updated controller-runtime to v0.11.0 to match k8s 23

Signed-off-by: ehila ehila@redhat.com

@openshift-ci openshift-ci Bot requested review from gnufied and tsmetana December 15, 2021 08:09
Comment thread diskmaker/api_updater.go

localv1 "github.com/openshift/local-storage-operator/api/v1"
"github.com/openshift/local-storage-operator/api/v1alpha1"
"github.com/prometheus/common/log"
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't sure if there was a reason why the prometheus log package was pulled in, they recently did a refactor to a different package. Since we're already using klog and zap directly, figured it might be easier to utilize klog instead. Should I refactor to pull this in if needed?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change looks fine, I think it was a mistake that LSO ever used this prometheus log package.

updated library-go
  - update to use default leader election configs based off of cluster topology
updated to k8s v0.23.0
updated controller-runtime to v0.11.0 to match k8s 23

Signed-off-by: ehila <ehila@redhat.com>
@eggfoobar
Copy link
Copy Markdown
Contributor Author

/assign @gnufied

Signed-off-by: ehila <ehila@redhat.com>
@gnufied
Copy link
Copy Markdown
Member

gnufied commented Dec 17, 2021

I think https://github.com/openshift/local-storage-operator/pull/299/files PR also moves all logging in LSO to klog. cc @dobsonj

@gnufied
Copy link
Copy Markdown
Member

gnufied commented Dec 17, 2021

/assign @dobsonj

updated library-go to latest for fix in pr openshift/library-go#1273

Signed-off-by: ehila <ehila@redhat.com>
@dobsonj
Copy link
Copy Markdown
Member

dobsonj commented Dec 20, 2021

/retest

@dobsonj
Copy link
Copy Markdown
Member

dobsonj commented Dec 20, 2021

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 20, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 20, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dobsonj, eggfoobar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 20, 2021
@dobsonj
Copy link
Copy Markdown
Member

dobsonj commented Dec 20, 2021

@eggfoobar can you create a bugzilla for this?

Signed-off-by: ehila <ehila@redhat.com>
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 21, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 21, 2021

@eggfoobar: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@eggfoobar
Copy link
Copy Markdown
Contributor Author

/retitle Bug 2034484: feat: bumped library-go
this PR pulls in the latest library-go and subsequent k8s 0.23.0 bump

@openshift-ci openshift-ci Bot changed the title feat: bumped library-go Bug 2034484: feat: bumped library-go Dec 21, 2021
@openshift-ci openshift-ci Bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Dec 21, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 21, 2021

@eggfoobar: This pull request references Bugzilla bug 2034484, which is invalid:

  • expected the bug to target the "4.10.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2034484: feat: bumped library-go

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@eggfoobar
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@openshift-ci openshift-ci Bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Dec 21, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 21, 2021

@eggfoobar: This pull request references Bugzilla bug 2034484, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (jhou@redhat.com), skipping review request.

Details

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci Bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Dec 21, 2021
@dobsonj
Copy link
Copy Markdown
Member

dobsonj commented Dec 21, 2021

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 21, 2021
@openshift-merge-robot openshift-merge-robot merged commit 4735615 into openshift:master Dec 21, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 21, 2021

@eggfoobar: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 2034484 has not been moved to the MODIFIED state.

Details

In response to this:

Bug 2034484: feat: bumped library-go

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants